Re: [NTG-context] Odd Font Behavior in startstop Group

2022-02-06 Thread śrīrāma via ntg-context
On Sunday, February 6, 2022 3:50:21 PM IST Wolfgang Schuster via ntg-context wrote: > The following two font settings are wrong, you're passing the name of a > typescript for the third argument while \definefontfamily expects the > family name of a font. > […] > ConTeXt already provides a

Re: [NTG-context] Odd Font Behavior in startstop Group

2022-02-06 Thread Wolfgang Schuster via ntg-context
Michael Urban via ntg-context schrieb am 05.02.2022 um 20:28: I am experiencing an odd behavior switching text styles in a defined startstop group ("blockquote"). I get different behavior depending on whether the switchtobodyfont in the startstop definition includes the dummy {\it

Re: [NTG-context] Odd Font Behavior in startstop Group

2022-02-05 Thread śrīrāma via ntg-context
On Sunday, February 6, 2022 12:58:06 AM IST Michael Urban via ntg-context wrote: > Do I need a newer version of ConTeXt, or am I doing something wrong? > Fonts in ConTeXt are always perilous, alas. For me, anyway. (pre)loading the typescripts 'fixes' the issue. \usebodyfont[termes] See

[NTG-context] Odd Font Behavior in startstop Group

2022-02-05 Thread Michael Urban via ntg-context
I am experiencing an odd behavior switching text styles in a defined startstop group ("blockquote"). I get different behavior depending on whether the switchtobodyfont in the startstop definition includes the dummy {\it } and {\bf } text. If they are not there, the italic an

Re: [NTG-context] [startstop]

2021-01-22 Thread Floris van Manen
On 22/01/2021 23:39, Wolfgang Schuster wrote: No \do...empty (LMTX only): \tolerant\protected\def\startzzz#=%   {\hrule    \doifsomething{#1}{\bold{\strut#1}\blank}} \protected\def\stopzzz   {\blank[10mm]} \starttext \startzzz \input weisman \stopzzz \startzzz{Ward} \input ward

Re: [NTG-context] [startstop]

2021-01-22 Thread Jairo A. del Rio
El vie, 22 de ene. de 2021 a la(s) 17:39, Wolfgang Schuster ( wolfgang.schuster.li...@gmail.com) escribió: > Jairo A. del Rio schrieb am 22.01.2021 um 23:14: > > How strange. I guess you don't have your modules installed. In such a > > case, you could install them from modules.contextgarden.net >

Re: [NTG-context] [startstop]

2021-01-22 Thread Wolfgang Schuster
Jairo A. del Rio schrieb am 22.01.2021 um 23:14: How strange. I guess you don't have your modules installed. In such a case, you could install them from modules.contextgarden.net and put content under texmf-modules so after mtxrun --generate and context

Re: [NTG-context] [startstop]

2021-01-22 Thread Jairo A. del Rio
How strange. I guess you don't have your modules installed. In such a case, you could install them from modules.contextgarden.net and put content under texmf-modules so after mtxrun --generate and context --make examples work. Another possibility is to use \do...empty and such, but it feels odd

Re: [NTG-context] [startstop]

2021-01-22 Thread Floris van Manen
unfortunately this does not work, 'annotation' is not found. But is it possible to give a start/stop definition user parameters? And if so, how? .F ___ If your question is of interest to others as well, please add

Re: [NTG-context] [startstop]

2021-01-22 Thread Jairo A. del Rio
Like this? \usemodule[annotation] %Thanks for this module, Wolfgang \defineannotation[zzz] \define[2]\AnnotationCommand {\doifelse{\placeannotationtitle}{}{}{\hrule\bf\placeannotationtitle\par}#2\blank[10mm]} \setupannotation[zzz] [alternative=command, command=\AnnotationCommand, text=]

[NTG-context] [startstop]

2021-01-22 Thread Floris van Manen
I'd like to create a start/stop command with a parameter \startzzz[a] one two three \stopzzz \startzzz[b] one two three \stopzzz How do i define/pass the tag parameter in the definition? This does not work (obviously) \definestartstop[zzz][ before={\hrule\bf tag\blank},

Re: [NTG-context] mailing list behaviour (was: Spurious newlines at beginning of startstop pair)

2019-11-29 Thread Marco Patzer
On Fri, 29 Nov 2019 12:10:46 +0100 Henning Hraban Ramm wrote: > The problem seems to be that traditional mailing lists like this just > don’t work with modern security standards. > > I didn’t check how secure NTG’s mail server is configured, but > changing subject and sender of every message is

Re: [NTG-context] mailing list behaviour (was: Spurious newlines at beginning of startstop pair)

2019-11-29 Thread Henning Hraban Ramm
> Am 2019-11-29 um 11:05 schrieb Denis Maier : > > Am 29.11.2019 um 10:38 schrieb Hans Hagen: >> Second: For some reasons I have not received your message. It wasn't in the >> Spam folder and I usually receive mails from the list. Any ideas? Are there >> some known problems? >> >> Your

Re: [NTG-context] Fwd: Re: Spurious newlines at beginning of startstop pair

2019-11-29 Thread Hans Hagen
On 11/29/2019 11:05 AM, Denis Maier wrote: Am 29.11.2019 um 10:38 schrieb Hans Hagen: Second: For some reasons I have not received your message. It wasn't in the Spam folder and I usually receive mails from the list. Any ideas? Are there some known problems? Your mailbox host does some

Re: [NTG-context] Fwd: Re: Spurious newlines at beginning of startstop pair

2019-11-29 Thread Denis Maier
Am 29.11.2019 um 10:38 schrieb Hans Hagen: Second: For some reasons I have not received your message. It wasn't in the Spam folder and I usually receive mails from the list. Any ideas? Are there some known problems? Your mailbox host does some strange address checking (we run a mail server

Re: [NTG-context] Fwd: Re: Spurious newlines at beginning of startstop pair

2019-11-29 Thread Hans Hagen
On 11/28/2019 11:26 PM, denis.maier.li...@mailbox.org wrote: Hans, thanks for your answer. But two questions: First: Am I right to assume that the important part is `\GetPar`. The rest is syntactic sugar to make to code more ConTeXt-like, right? what you do is something: \def\foo{something

[NTG-context] Fwd: Re: Spurious newlines at beginning of startstop pair

2019-11-28 Thread denis . maier . lists
Hans, thanks for your answer. But two questions: First: Am I right to assume that the important part is `\GetPar`. The rest is syntactic sugar to make to code more ConTeXt-like, right? Second: For some reasons I have not received your message. It wasn't in the Spam folder and I usually receive

Re: [NTG-context] Spurious newlines at beginning of startstop pair

2019-11-27 Thread Hans Hagen
On 11/27/2019 2:17 PM, Denis Maier wrote: Hi, I have this file: -- \newdimen\cslhangindent \cslhangindent=1.5em \definestartstop [cslreferences] [         before={%         \setupnarrower[left=\cslhangindent]        

[NTG-context] Spurious newlines at beginning of startstop pair

2019-11-27 Thread Denis Maier
Hi, I have this file: -- \newdimen\cslhangindent \cslhangindent=1.5em \definestartstop [cslreferences] [         before={%         \setupnarrower[left=\cslhangindent]         \startnarrower[left]%        

Re: [NTG-context] startstop, narrower and switchtobodyfont gives strange interlinespace

2017-03-22 Thread Andres Conrado
This works for me, is probably not what you want, but at leat it's consistent (it uses the interline of the main text). \definestartstop[passus][ before={\startnarrower}, after={\stopnarrower}, style={\tfxx}, ] \starttext \subject{It looks OK here:} \input knuth \startnarrower \tfxx \input

Re: [NTG-context] startstop, narrower and switchtobodyfont gives strange interlinespace

2017-03-22 Thread Alan Braslau
On Wed, 22 Mar 2017 20:38:01 +0100 "Mikael P. Sundqvist" wrote: > What am I doing wrong? Any ideas to solve it Add a \par: \input knuth\par Alan ___ If your question is of interest to others as

Re: [NTG-context] startstop, narrower and switchtobodyfont gives strange interlinespace

2017-03-22 Thread Mikael P. Sundqvist
On Wed, Mar 22, 2017 at 8:38 PM, Mikael P. Sundqvist wrote: > Hi, > > with the latest standalone, the file below runs, but gives strange > results. Look at the interline space in the last paragraph (starting > with "But a system...") of the document. It is too big. Resulting pdf

[NTG-context] startstop, narrower and switchtobodyfont gives strange interlinespace

2017-03-22 Thread Mikael P. Sundqvist
Hi, with the latest standalone, the file below runs, but gives strange results. Look at the interline space in the last paragraph (starting with "But a system...") of the document. It is too big. Resulting pdf is attached. What am I doing wrong? Any ideas to solve it (i.e. to be able to define

[NTG-context] tagging a startstop

2015-03-28 Thread Idris Samawi Hamid ادريس سماوي حامد
to say, e.g. \definestartstop[TAG][tag=div] % or tag=construct etc. so that my startstop also generates tags in the xhtml. Is there already a way to do this? Thanks and Best Wishes Idris -- Idris Samawi Hamid Professor of Philosophy Colorado State University Fort Collins, CO 80523

Re: [NTG-context] tagging a startstop

2015-03-28 Thread Wolfgang Schuster
with \dostarttagged etc but could not get it to work (too low-level for me I guess). What would be nice is to be able to say, e.g. \definestartstop[TAG][tag=div] % or tag=construct etc. so that my startstop also generates tags in the xhtml. Is there already a way to do this? Commands created

Re: [NTG-context] \noindent in startstop block is no t working on the text that follows the block

2008-02-08 Thread Bart Wise
Thanks Taco! On Friday February 8 2008, Taco Hoekwater wrote: Bart C. Wise wrote: I defined a startstop block. However, the text that follows the block I don't want to be indented. Code \definestartstop[Center][ before={\startalignment[center]}, after={\stopalignment

[NTG-context] \noindent in startstop block is not working on the text that follows the block

2008-02-07 Thread Bart C. Wise
I defined a startstop block. However, the text that follows the block I don't want to be indented. Code \definestartstop[Center][ before={\startalignment[center]}, after={\stopalignment\noindent} ] \starttext \startCenter This is some text! \stopCenter I don't want this paragraph

Re: [NTG-context] \noindent in startstop block is not working on the text that follows the block

2008-02-07 Thread Taco Hoekwater
Bart C. Wise wrote: I defined a startstop block. However, the text that follows the block I don't want to be indented. Code \definestartstop[Center][ before={\startalignment[center]}, after={\stopalignment\noindent} ] You want \noidentation (instead of \noindent). Best

[NTG-context] Re: Collecting command arguments in a startstop environment

2004-08-02 Thread Patrick Gundlach
[...] Anyhow, I'm finding myself wanting to do this in ConTeXt, with of course replacing \newenvironment with \definestartstop. I didn't want to fiddle with \definestartstop, but here is a quick hack: -- \long\def\foo#1{ Hello #1!}

Re: [NTG-context] Re: Collecting command arguments in a startstop environment

2004-08-02 Thread Brooks Moses
At 01:37 AM 8/2/2004, you wrote: Anyhow, I'm finding myself wanting to do this in ConTeXt, with of course replacing \newenvironment with \definestartstop. I didn't want to fiddle with \definestartstop, but here is a quick hack: -- \long\def\foo#1{

Re: [NTG-context] Collecting command arguments in a startstop environment

2004-08-02 Thread Brooks Moses
To answer my own question: At 10:39 PM 8/1/2004, I wrote: There's a nice little problem that arises in LaTeX, of wanting to write a bit of code like the following, to define an environment that passes the contents of the environment to a command as an argument: \newcommand{\foo}[1]{...}

[NTG-context] Collecting command arguments in a startstop environment

2004-08-01 Thread Brooks Moses
There's a nice little problem that arises in LaTeX, of wanting to write a bit of code like the following, to define an environment that passes the contents of the environment to a command as an argument: \newcommand{\foo}[1]{...} \newenvironment{fooenv}{% \foo\bgroup }{% \egroup